Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The EDB Postgres Advanced Server must be able to generate audit records when successful accesses to objects occur.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-213661 | PPS9-00-012400 | SV-213661r508024_rule | Medium |
| Description |
|---|
| Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE |
| STIG | Date |
|---|---|
| EDB Postgres Advanced Server Security Technical Implementation Guide | 2022-06-13 |
Details
| Check Text ( C-14883r290295_chk ) |
|---|
| Execute the following SQL as enterprisedb: SHOW edb_audit_statement; If the result is not "all" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding. |
| Fix Text (F-14881r290296_fix) |
|---|
| Execute the following SQL as enterprisedb: ALTER SYSTEM SET edb_audit_statement = 'all'; SELECT pg_reload_conf(); or Update the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement. |